Methods and systems for performing redirects to a search engine

ABSTRACT

The present invention is related to methods and systems for processing search requests and for performing searches over a network. In an embodiment, a recipient designation is received from a user over a network. The designation indicates that future searches performed by the user are to be associated with the recipient (even if the subject matter of the search is not related to the recipient). A search request is received from the user; causing a search to be performed in response to the search request. An identifier corresponding to the recipient is stored in association with an indication regarding the occurrence of the first search request.

PRIORITY CLAIM

This application is a continuation of U.S. application Ser. No.13/444,671, filed Apr. 11, 2012, which is a continuation of U.S.application Ser. No. 13/029,083, filed Feb. 16, 2011, now U.S. Pat. No.8,161,029, which is a continuation of U.S. application Ser. No.12/843,516, filed Jul. 26, 2010, now U.S. Pat. No. 7,895,182, which is acontinuation of U.S. application Ser. No. 11/507,954, filed Aug. 22,2006, now U.S. Pat. No. 7,769,738, which claims priority from U.S.Patent Application No. 60/710,181, filed Aug. 22, 2005, now expired, andU.S. Patent Application No. 60/737,477, filed Nov. 17, 2005, nowexpired. The entire disclosure in the priority applications is herebyincorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention is related to systems and methods for processingsearch requests and for performing searches over a network.

2. Description of the Related Art

The World Wide Web includes Internet servers hosting Web pages. A Webpage may include, for example, links to other Web pages or resources,text, graphics, audio, and/or video content. A Uniform Resource Locator(URL) provides or indicates that address to a resource, such as Webpage. There are currently several billion Web pages.

In order to aid users locate Web page information, a variety of searchengines have been developed and deployed. Search engines typically indexWeb pages, and provide a search interface that can be accessed at acorresponding URL via a user browser or otherwise. The search interfacecan include a search field, via which a user can enter search terms. Thesearch engine then searches for Web pages that correspond to the searchterms. The search results, or a portion thereof, are then returned tothe user via the user browser.

Certain search engine provide pay per click, or PPC, advertising. Payper click advertisements may be in the form of advertisements placedadjacent to the search results. When a user clicks on the advertisement,the advertiser may be charged. Similarly, certain search engines providepay for placement and pay for ranking, wherein a customer can pay thesearch engine operator to achieve higher or more prominent placement inthe search results.

SUMMARY OF THE INVENTION

The present invention is related to systems and methods for processingsearch requests and for performing searches over a network.

An example embodiment provides a system for redirecting search requestsover a network, the system comprising: a database that storesidentification information for a plurality of recipients, wherein therecipients are eligible to receive a benefit as the result of searchesperformed by individuals; and program code stored in computer readablememory configured to: provide a user interface to a user terminal viawhich a user can identify a recipient; determine if the recipientidentified by the user corresponds to a recipient identifier stored inthe database; store an association between the user terminal and theidentified recipient; receive a search request from the user; store anindication that the search request was received in association withidentified recipient information; forward the search request to a Website associated with a search engine; determine a payment allocationwith respect to the identified recipient based at least in part on theindication that the search request was received from the user.

An example embodiment provides a method of redirecting search requestsover a network, the method comprising: receiving over a network arecipient designation manually provided by a user, wherein recipientsare eligible to receive a benefit as the result of searches performed byindividuals; storing the recipient designation in computer readablememory; receiving at a first website a first search request from theuser; forwarding the first search request to an second Internet siteassociated with a search engine, wherein the search engine will generatesearch results at least partly based on the forwarded first searchrequest; storing in association with an identifier corresponding to therecipient an indication regarding the occurrence of the first searchrequest; and allocating a payment to the recipient based at least inpart on the indication.

An example embodiment provides a method of redirecting search requestsover a network, the method comprising: receiving a recipient designationfrom a user over a network; searching a database to determine if arecord exists in the database for the designated recipient; if thedatabase includes a record for the designated recipient, storing anindication that the user designated the recipient in computer readablememory; receiving at a first website a first search request from theuser; providing the first search request to a second site associatedwith a search engine, wherein the search engine will generate searchresults at least partly based on the first search request; storing inassociation with an identifier corresponding to the recipient anindication regarding the occurrence of the first search request; andallocating a payment to the recipient based at least in part on theindication.

An example embodiment provides a method of processing search requestsover a network, the method comprising: receiving a recipient designationfrom a user over a network that indicates that future searches performedby the user are to benefit the recipient (even if the subject matter ofthe search is not related to the recipient); determining or identifyingif the recipient is a non-profit entity; receiving at a first website ortoolbar a first search request from the user; causing a search to beperformed in response to the first search request; storing inassociation with an identifier corresponding to the recipient anindication regarding the occurrence of the first search request; andallocating a payment to the recipient based at least in part on theindication.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments are illustrated in the accompanying drawings,which are for illustrative purposes only. The drawings comprise thefollowing figures, in which like numerals indicate like parts.

FIG. 1 illustrates an example networked system.

FIG. 2 illustrates an example process for redirecting search queries andfor tracking the same;

FIG. 3 illustrates an example recipient selection form.

FIG. 4 illustrates a recipient submission form.

FIG. 5 illustrates an example report.

FIGS. 6A-B illustrate example administration forms.

FIG. 7 illustrates another example administration form.

FIG. 8A-B illustrates example search tool bars.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The present invention is related to systems and methods for processingsearch requests and for performing searches over a network, such as byoptionally redirecting search queries to a search engine.

Throughout this disclosure, the term “website” is used to refer to auser-accessible server site that implements the basic World Wide Webstandards for the coding and transmission of hypertext documents. Thesestandards currently include the hypertext markup language (HTML) and thehypertext transfer protocol (HTTP). The term “site” is not intended toimply a single geographic location, as certain websites or other networksites include multiple geographically distributed computer systems thatare appropriately linked together. Furthermore, while this disclosuredescribes certain embodiments that use the Internet and relatedprotocols, other networks, such as networked interactive televisions,and other protocols are used in other embodiments.

Additionally, unless otherwise indicated, the functions described hereinare performable by software modules including executable code andinstructions running on one or more general purpose computers. In anexemplary embodiment, the computers include one or more centralprocessing units that execute program code and process data. Thecomputers also include memory, including one or more of volatile memory(such as random access memory for temporarily storing data and datastructures during program execution), non-volatile memory (such as ahard disc drive, optical drive, or flash drive, for storing programs,data, and databases), and one or more network interfaces for accessingan intranet and/or Internet.

The computers optionally include a display for displaying userinterfaces, data, photographs, images, and the like. In certainembodiments, the computers also include one or more user input devices,such as a keyboard, mouse, pointing device, microphone and the like,used to navigate, provide commands, enter information, and the like.However, other embodiments are implemented using special purposecomputers, state machines, and/or hardwired electronic circuits.Additionally, the example processes described herein do not necessarilyhave to be performed in the described sequence, and not all states haveto be reached or performed.

Furthermore, where this disclosure refers to “clicking on” a link orbutton, or pressing a key in order to provide a command or make aselection, in other embodiments the commands or selections are madeusing other input techniques, such as using voice input, pen input, ormouse input, including hovering over an input area, selecting menuoptions, and the like.

FIG. 1 illustrates an example system embodiment that can be used inconjunction with the processes described herein. Other systems andarchitectures can be used as well. With reference to FIG. 1, one or moreuser terminals 102, 104, 106 are coupled to a redirection system 107over a network 110, such as the Internet. By way of example, a userterminal can be a personal computer, a networked personal digitalassistant, a networked, interactive television or other entertainmentsystem, a wireless or wired phone, and so on. The user terminals canhost a browser or other appropriate network resource user interface.

The example redirection system 104 includes a front end server 108 thathandles communications with user terminals, serves Web pages, andperforms search request forwarding. The example redirection system 107further includes a user database 114 and a recipient database 112.Optionally, the user and recipient databases are implemented as a singledata store. The term “recipient” will be explained in greater detailbelow. The example redirection system 107 hosts an administrationapplication 116, which tracks the number of hits received for eachrecipient, provides for entry and maintenance of recipient information,and generates reports.

The redirection system 107 can be used to redirect search requestsentered into a search field on a redirection system Web page to a searchengine 118. Optionally, the search engine 118 can be operated by a thirdparty. By way of example, the search engine 118 can be a general purposesearch engine, such as that operated by Google or Yahoo, or can be aspecial purpose search engine, such as a shopping comparison searchengine that checks prices at various online stores or locates e-commerceoutlets based on a user product-related query, such as Nextag,Pricecomparison.com, or Froogle. Other examples include search enginesthat search news Web sites, blog sites, and/or that search forphotographs, videos, music, or other content. Optionally, the searchengines may be configured to narrow a search to a particular type ofcontent (e.g., news, blogs, photographs, videos, music, etc.) or toseveral user specified types of content. The redirection system 107 canfurther be used to redirect queries to an electronic commerce site(e.g., an online store, shopping comparison website, product reviewsite, music, video, and/or image download site, etc.) or other types ofwebsites that pay commissions or referral fees for such redirection orreferral. Optionally, certain users can be blocked from utilizing theredirection system. For example, certain IP (Internet Protocol)addresses known or suspected to be associated with users trying to cheator abuse the system (e.g., by performing searches using robots toincrease funds allocated to a recipient) can be blocked. Optionally, iffraudulent search activity is detected which is being performed onbehalf of a designated recipient, the designated recipient is delistedand will not receive further recipient funds via the process describedherein.

The redirection system 107 can forward or redirect a search query (e.g.,in the form of a text search string) by adding the URL associated withthe search engine 118 to the URL (or other identifier) associated withthe redirection system and the query. For example, if the search queryphrase/string is “movies”, and the URL for the redirection systemwebsite is www.goodsearch.com, and the URL for the search engine iswww.searchengine.tdl, then redirection system 107 may redirect thesearch request using the example URL:

www.searchengine.tdl/custom?q=movies%2F˜www.goodsearch.com.

As will be discussed in greater detail below, a user can select aneligible recipient (e.g., a charity or non-profit entity) via theredirection system 107. When the user thereafter performs a search usingthe search engine 118 by going through the redirection system 107, theselected recipient will accrue, receive and/or be entitled to a fee.

By way of illustration, the search engine or electronic commerce siteoperator may agree to pay an amount to the redirection system operatorperiodically or for a certain period of time (e.g., a month, a quarter,etc.) at least partly in exchange for searches routed to the searchengine 118 via the redirection system 107. By way of example, the amountcan be a fixed amount per period and/or the amount can be based on thenumber of searches directed to the search engine 118 by the redirectionsystem 107. The redirection system operator can then divide the amount,or a portion thereof, among the designated recipients based, in part, onthe number of times users that have selected the recipient perform asearch via the search engine. For example, for Recipient_(A), the feeallocation can be calculated as follows:

Recipient fee for Recipient_(A)=(total amount to be paid to recipientsfor a selected time period)×(number of eligible searches performed byusers that have selected Recipient_(A))/(total number of eligiblesearches)

Thus, when a user performs a search via the redirection system Web site,the redirection system determines who the user had designated as arecipient, and counts the search as a “hit” for that recipient. Theredirection system operator can then periodically make payments torecipients based on the recipient fee calculation (e.g., every month,quarter, year, etc.).

Advantageously, using the foregoing example fee allocation process, thesearch engine operator (or other commerce site operator to which theuser was redirected) does not need to track which users performed asearch and does not need to be aware of the identity of the recipients.Further, because the search engine operator is optionally not aware ofthe identity of the recipients, the user's privacy is better assured.However, in other embodiments, the search engine or other operator canbe provided with information regarding the user and/or the designatedrecipient for a given search request.

For example, optionally, in addition to an identifier associated withthe redirection system 107 (e.g., www.goodsearch.com), the redirectionsystem 107 can include an identifier related to the user and/or anidentifier related to recipient in the redirected search request URL.This information enables the search engine 118 to track the number ofsearches forwarded by the redirection system 107, the number of searchesoriginated with the user, and/or the number of searches for which agiven recipient will benefit. The search engine 118 can store theforegoing information in its own data store. Optionally, the searchengine operator can base current or future payments to the redirectionsystem operator, the designated recipient, and/or the user based on someor all of the foregoing tracked information.

The amount paid to recipients can be performed by different processes aswell. For example, the recipient may receive a percentage of the fee thesearch engine operator receives for a given search or that a commercesite makes for a sale. By way of further example, the recipient mayreceive a fixed amount per month, per year, or per other designatedperiod for each user that selected the recipient. Optionally, payment ismade to the recipient only if the amount due to the recipient is equalto or greater than a predetermined threshold (e.g., $50 or $100).

The user database 114 will now be described. The user database 114 isused to store user information. For example, the user database 114 canstore user identification information. The user identification caninclude one or more of a cookie ID, a user identifier, and/or apassword. By way of example, a cookie can be packet of information sentby the redirection system 107 to the user browser and stored on the userterminal. The cookie can then be sent back to the redirection system 107by the browser when the browser accesses the redirection system 107. Thecookie is optionally used to automatically authenticate or identify theuser of the redirection system 107 as part of their initial siteregistration or login process without requiring the user to manuallysign in. Optionally, the cookie does not identify a person individually,but identifies the combination of the terminal and the web browser.

Optionally, the user can be requested to enter a user identifier and/ora password into a logon interface provided by the redirection system 107via the user browser. The redirection system 107 can then compare useridentifier and/or password with that stored in the user database toidentify the recipient previously selected by the user. This will enablethe user to access the redirection system 107 and accrue fees for theuser's designated recipient, while utilizing different terminals whichdo not have the user's original cookie stored thereon and without havingto reselect the recipient. The user database 114 can optionally alsostore an identifier associated with the eligible recipient selected bythe user in association with an identifier corresponding to the user.

The example recipient database 112 will now be described. The recipientdatabase 112 includes identifiers and related information for“recipients” (e.g., active eligible recipients of search generatedrevenues, pending recipient submissions that have not yet been approved,rejected entities that have been determined to be non-eligible to berecipients, etc.) which can be stored in the form of records. Forexample, the recipient database 112 can include the recipient name,description, category (e.g., college, high school, middle school,elementary school, orphanage, military, non-profit, religious, etc.),recipient contact person, recipient address, recipient phone number,recipient email address, submitter name (the user that requested thatthe recipient be added to the database), submitter email, othersubmitter contact information, recipient status (e.g., active, pending,rejected, hidden). In this example, “hidden” can mean that the recipientis inactive. For example, a charity or other recipient that has moneyaccrued but is no longer active (e.g., no longer in existence or unableto receive the money).

The recipient eligibility criteria can, for example, optionally requirethat the recipient be a non-profit entity, a public charity, a school, ahospital or meet other criteria. By way of further example, and notlimitation, the criteria can optionally include the presence of therecipient's name on a government list of non-profits or charities, suchas Publication 78, Cumulative List of Organizations described in Section170(c) of the Internal Revenue Code of 1986. Thus, for example, aneligibility check can be performed automatically by the redirectionsystem 107 accessing a government or other list of approved charities,or the eligibility check can be performed manually.

Several example user and administrator interfaces will now be described.FIG. 3 illustrates an example recipient selection form which canoptionally be provided as a Web page to the user terminal. A selectionfield 302 is provided via which a user can enter a recipient name (e.g.,a charity, school, or other recipient). The redirection system 107 thensearches the recipient database 112 to determine if the recipient iseligible to receive search generated fees. The search optionally willlocate recipients that include any of the search terms entered by theuser and display the results to the user in the order of relevance, oralphabetically, or otherwise ordered. The user can then select arecipient from the list by clicking on a recipient name or select buttonor link.

If the redirection system 107 fails to locate any matches for therecipient name entered by the user, or the recipient has a rejectedstatus, the user is so informed and the user can attempt to submitanother name. In addition, a listing of eligible recipients can bedisplayed to the user, and the user can click on a select button or linkto thereby select a recipient. The user can optionally request that thelisting be alphabetically sorted, sorted by state, sorted by category,or by other fields.

Optionally, the user can click on a link, such as a “add charity” field(not shown), via which the user can request that an entity be added tothe eligible recipient list using a form, such as that illustrated inFIG. 4. The user can activate a “clear selection” control 306 to deletethe current entry in the charity selection field 302. The user canactivate an “amount raised” control 308 and the system will generate areport listing the total amount of charity raised overall and/or in aspecified period for the charity listed in field 302.

As depicted in FIG. 3, a search field 304 is further provided via whichthe user can search the Web (or other target data source). This searchfield is optionally also provided on a separate Web page that does notinclude the recipient selection field. The separate Web page optionallyincludes a logo or other identifier associated with the redirectionsystem operator/owner and optionally further includes a logo or otheridentifier associated with the search engine operator/owner. Asdescribed elsewhere herein, the search field can also be provided via atoolbar.

Even though the separate Web page with the search field may be used toprovide the search terms to the search engine 118, the URL displayed inthe user's browser will optionally be that associated with theredirection system 107, rather than that of the search engine 118. Thus,in one embodiment, URL cloaking is optionally used, that uses an HTMLframe set. For example, the displayed URL can be:

-   -   http://www.goodsearch.com

and the URL of the hidden frame is:

-   -   http://www.searchengine.tld/˜goodsearch.com.

This cloaking technique will leave http://www.goodsearch.com in the userbrowser's address bar.

FIG. 4 illustrates an example recipient submission form via which a usercan propose that an entity be added as an eligible recipient. In thisexample, the form has been configured for entities that are charitableor non-profit. The example form includes fields via which the user canenter one or more of the proposed recipient name, description, therecipient category (e.g., college, elementary school, high school,middle school, military, nonprofit, etc.), a recipient contact,recipient address, recipient phone number, recipient email, the user'sname, and the user's email address. Other fields can be provided aswell, such as a tax ID field. If the submitted entity meets therecipient eligibility criteria, the redirection system can add theentity, and the corresponding information provided by the user, into therecipient database 112 with an active status. If the submitted entitydoes not meet the recipient eligibility criteria, the redirection systemcan add the submitted entity, and corresponding information provided bythe user, into the recipient database 112 with a rejected status.

The administration application 116 and associated user interfaces willnow be described in greater detail. The administration application 116tracks how many times a given eligible recipient was selected by users,and how many times the corresponding users conducted a search. Forexample, when a user accesses the redirection system website, theredirection system 107 reads the user's cookie to access the cookie ID(or optionally determines which user is accessing the website via a userID and/or password entered into corresponding webpage fields), and basedon the identification information, determines which entity the user hadpreviously selected as the recipient. Optionally instead, the recipientidentifier can be stored in the user cookie and retrieved by theredirection system 107. In either case, if the user then performs asearch using the search engine 118, the administration application 116records a “hit” in the recipient database 112 in association with therecipient record. Optionally, the redirection system 107 can identifyand record which user is responsible for a given hit and store suchinformation in the recipient and/or user databases.

The redirection system 107 also provides administration functions usedto generate reports and administer the recipient database 112.Optionally, to access the administration functions, a user may need toenter authorization information, such as a user ID and password. Theadministration application 116 optionally includes a report generatorthat provides an activity report that provides some or all of thefollowing information: the recipient name, the recipient state, therecipient city, the number of hits (the number of times a user who hasselected the recipient performed a search via the redirection system),and the current percentage of hits for the recipient as compared to atotal number of hits for all eligible recipients (or a selected subsetthereof). FIG. 5 illustrates an example activity report.

As illustrated in FIG. 5, fields are provided via which a reportrequester can specify the start and end dates for which the report is tobe generated, or the month and the year of which the report is to begenerated. If the report is for a requested period, the number of hitsreported will be for the hits that occurred during the requested period,and the percentage will be the percentage of hits for the recipientduring that period as compared to a total number of hits for alleligible recipients (or a selected subset thereof) during that period.By way of further example, for a given charity (or as a total) for aselected time frame, the report can provide some or all of the followinginformation:

The number of searches performed;

The number of times a link in search results were clicked on (orotherwise selected) by a user;

The percent of total searches a given recipient received credit for;

The percent of total search result “link clicks”;

The report can be presented on a terminal screen via a browser, printedout, or otherwise presented.

When the activity report is electronically presented on a terminalscreen, the activity report can be sorted by clicking on a desiredfield. For example, clicking on the “name” field causes the report to besorted by recipient name. Similarly, clicking on the “percentage” fieldcauses the report to be sorted by percentage. Optionally, the reportgenerator can generate a report that lists the users that have selecteda given recipient.

In addition, an entity administration form is provided by redirectionsystem 107 that lists the entities stored in the recipient database 112.The report can list the name, city, state, status, and record creationdate for that entity. An administrator can delete an entity record byactivating the delete control, or edit an entity record by activatingthe edit control. The administrator can request a filtered list based onentity status, entity category, entity state, and a search term (e.g.,part of an entity name) by entering or selecting the filter criteria viacorresponding filter fields and by activating the search control. FIG.6A illustrates an example entity report filtered to only display thoseentities that include the string “cedars”. In this example, the entitiesare charitable entities. FIG. 6B illustrates another example reportlisting recipients whose names being with the letter “A”. A “resetsearches” control is provided via which an administrator can reset tozero the search total (e.g., the number of hits) for the correspondingrecipient.

FIG. 7 illustrates an example entity form which can be used to enter oredit entity information stored in the recipient database 112. Theexample form includes fields for the recipient name, description, therecipient category (e.g., college, elementary school, high school,middle school, military, nonprofit, etc.), a recipient contact,recipient address, recipient phone number, recipient email, thesubmitting user's name, the submitting user's email address, and therecipient status (e.g., active, pending, rejected, hidden). Other fieldscan be provided as well, such as a tax ID field (not shown).

FIG. 2 illustrates an example search redirection process. At state 202,a user accesses the redirection system website via a browser. At state204, the redirection system reads a cookie from the user terminal. Atstate 206, the redirection system receives a search query from the user.At state 208, the redirection system forwards the search request to thesearch engine by prefixing the redirection system URL with the searchengine URL, with the search query embedded in the combined URLs. Atstate 210, the search results are presented to the user. At state 212,the redirection system determines which recipient the user haddesignated, and records a hit for that recipient.

While the above example includes a redirection system that redirectsqueries to a search engine, in another embodiment, the search engineitself provides the functionality of the redirection system, except thatthe redirection itself need not be provided. For example, the searchengine can include the recipient and user databases, as well as theadministrative application. Thus, the search engine can provide the userinterface that allows a user to designate recipients, track hitsassociated with recipients, calculate percentages of payment allocationsper recipient, receive and process requests to add eligible recipients,provide payments to eligible recipients, perform some or all of theother functions described elsewhere herein, etc.

Optionally, a toolbar may be downloaded for the redirection system site,a search site, or from another site to the user terminal (e.g., byactivating a toolbar download link presented via the homepageillustrated in FIG. 3). For example, the toolbar can be downloaded to,and visible from the user terminal browser (e.g., docked to thebrowser), the terminal desktop, a word processor, email client, orotherwise. A charity selection field (e.g., in the form of a drop-downmenu or a search field) is optionally provided via which the user canselect a charity. By way of example, the charity selection process canoptionally be performed as described above with respect to FIG. 3. Forexample, a user can enter a recipient name (e.g., a charity, school, orother recipient). The redirection system then searches the recipientdatabase to determine if the recipient is eligible to receive searchgenerated fees. The search optionally will locate recipients thatinclude any of the search terms entered by the user and display theresults to the user in the order of relevance. The user can then selecta recipient from the list by clicking on a recipient name or selectbutton or link. Once the charity name appears in the charity selectionfield, the user can activate a select charity button, and the selectedcharity will be the recipient of benefits received as a result ofsearches performed by the user via the toolbar search field, describedbelow. Optionally, the toolbar does not include a charity field. Forexample, for certain browsers the toolbar optionally does not include acharity field, while for other browsers the toolbar optionally doesinclude the charity field. Optionally, the user may select (e.g., via atoolbar menu) whether the toolbar displays the charity field.Optionally, the system accesses the cookie generated and stored on theuser's computer (when the user selected the charity on the systemhomepage), and when the user later performs a search using the toolbaror Web page, the system accesses the cookie, reads the charity recipientdesignation stored therein, and credits the charity accordingly.

A keywords search field is optionally provided via which the user canprovide search terms. A control is provided via which the user canselect which search engine (e.g., Yahoo, Google, MSN, etc.) is to beused to perform the search. When the user submits a search request, theredirection system performs the redirection process to the search engineas described herein, and tracks the searches to generate revenue for theselected charity.

Optionally, a control is provided via which the user can clear thesearch history of searches performed using the toolbar. Optionally, asupport control is provided, that when activated, displays helpinformation and/or generates an email in which the user can insert textidentifying a problem or issue and asking for help. Optionally a controlis provided, which, when activated by the user, causes a home page orother Web page associated with the redirection system to be presented.Optionally, the toolbar includes a pop-up blocker control and softwarewhich, when activated by the user, causes pop-up windows to be blocked.Optionally, a highlight control is provided as well. An example toolbaris illustrated in FIG. 8A, which includes a logo 802A associated withthe redirection system operator, a search field 804A (which optionallykeeps a record of previous search terms entered by the user which can berecalled as the user enters a search term), a search activation control806, a recipient selection field 808A, a select recipient control 810A(which, when activated by the user, causes the charity entered in field808A to be submitted to the system), a highlight control 812, and apop-up blocker control 814A. Additional, fewer, or different controlsand/or fields can be provided. FIG. 8B illustrates another exampletoolbar similar to the illustrated in FIG. 8A.

Although this invention has been disclosed in the context of certainembodiments and examples, it will be understood by those skilled in theart that the present invention extends beyond the specifically disclosedembodiments to other alternative embodiments and/or uses of theinvention and obvious modifications and equivalents thereof. Inaddition, while a number of variations of the invention have been shownand described in detail, other modifications, which are within the scopeof this invention, will be readily apparent to those of skill in the artbased upon this disclosure. It is also contemplated that variouscombinations or subcombinations of the specific features and aspects ofthe embodiments may be made and still fall within the scope of theinvention. Accordingly, it should be understood that various featuresand aspects of the disclosed embodiments can be combined with orsubstituted for one another in order to form varying modes of thedisclosed invention. Thus, it is intended that the scope of the presentinvention herein disclosed should not be limited by the particulardisclosed embodiments described above.

What is claimed is:
 1. A system for processing search requests receivedover a network, the system comprising: a data store that storesidentification information for a first plurality of recipients, whereinthe first plurality of recipients are eligible to receive a benefit atleast partly as the result of searches performed by individuals; acomputing device; and program code stored in computer readable memorythat when executed by the computing device is configured to: provide auser interface to a user terminal via which a user can identify arecipient at least from the plurality of recipients whose identificationinformation is stored in the data store; receive a search request fromthe user over the network; store in a data store an indication relatingto the search request received from the user terminal; facilitating asearch to be performed corresponding to the search request; determine apayment allocation with respect to the identified recipient, wherein thepayment allocation is related to the search request received from theuser, wherein the user is same user providing the recipient designation,even when the search request subject matter is unrelated to thedesignated recipient.